Skip to content

Add cre workflow logs command#262

Open
nadahalli wants to merge 3 commits intomainfrom
add-workflow-logs-command
Open

Add cre workflow logs command#262
nadahalli wants to merge 3 commits intomainfrom
add-workflow-logs-command

Conversation

@nadahalli
Copy link
Contributor

Summary

  • Adds cre workflow logs <workflow-name> subcommand that queries the GraphQL API for execution history
  • Shows timestamps, status, duration, and error details for failed executions
  • Supports --follow / -f for continuous polling (like tail -f) and --limit / -n to control page size
  • Takes a workflow name directly (no project folder required), only needs credentials

Example output

Workflow: blocknumber-tracker-staging

TIMESTAMP                 STATUS        DURATION    EXECUTION ID
2026-02-12T15:58:00Z      failure       1.0s        b14b7903
  -> confidential-http@1.0.0-alpha: [2]Unknown: Private:method SendRequest not found
2026-02-12T15:59:00Z      failure       1.0s        2b40e730
  -> confidential-http@1.0.0-alpha: [2]Unknown: Private:method SendRequest not found
2026-02-12T16:00:01Z      failure       0ms         e5d860c8
  -> confidential-http@1.0.0-alpha: [2]Unknown: Private:method SendRequest not found

Notes

  • Uses existing workflowExecutions and workflowExecutionEvents GraphQL queries (same as the web dashboard)
  • Excluded from isLoadSettings in root.go since it doesn't need a project folder or workflow settings
  • UX difference from other workflow subcommands: takes <workflow-name> directly instead of <workflow-folder-path> since it's a read-only query, not a contract interaction

Queries the GraphQL API for workflow execution history, showing
timestamps, status, duration, and error details for failures.

Supports --follow for continuous polling and --limit to control
how many recent executions to display.
@nadahalli nadahalli requested a review from a team as a code owner February 12, 2026 16:44
@github-actions
Copy link

👋 nadahalli, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

Suppress errcheck on io.Copy in test helper, regenerate docs.
* Truncate long errors keeping the diagnostic tail

Drop the first 40% of long error messages (>80 chars) since the
useful diagnostic info (e.g. PCR mismatches) sits at the end,
after layers of generic wrapping.

* Truncate long errors keeping head and diagnostic tail

For errors >120 chars, show the beginning + "..." + last 40%.
Nested error wrapping puts the useful diagnostic (e.g. PCR
mismatches) at the end; this keeps both ends visible.
@github-actions
Copy link

⚠️ Abigen Fork Check - Update Available

The forked abigen package is outdated and may be missing important updates.

Version Value
Current Fork v1.16.0
Latest Upstream v1.17.0

Action Required

  1. Review abigen changes in upstream (only the accounts/abi/bind directory matters)
  2. Compare with our fork in cmd/generate-bindings/bindings/abigen/
  3. If relevant changes exist, sync them and update FORK_METADATA.md
  4. If no abigen changes, just update the version in FORK_METADATA.md to v1.17.0

Files to Review

  • cmd/generate-bindings/bindings/abigen/bind.go
  • cmd/generate-bindings/bindings/abigen/bindv2.go
  • cmd/generate-bindings/bindings/abigen/template.go

⚠️ Note to PR author: This is not something you need to fix. The Platform Expansion team is responsible for maintaining the abigen fork.

cc @smartcontractkit/bix-framework

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments